Microsoft Sentinel Solutions Documentation

This documentation provides comprehensive information about Microsoft Sentinel Solutions, including data connectors, log tables, content items, parsers, and ASIM parsers.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

Overview

Counts below describe the existing documentation pages, except for collection methods and ASIM products. Catalog entries can share a page, so page totals can differ from the totals in the indexes and statistics.

Resource Count Details
Solutions 584 Individual solution pages
Connectors 724 Unique connector IDs and individual connector pages
Methods 13 Data collection methods
Tables 2,529 Individual table pages
Content 6,976 Content pages; the index lists 7,650 catalog entries
Parsers 725 Non-ASIM KQL function pages; the index lists 745 parsers
ASIM Parsers 247 231 source, 16 unifying, 0 empty parsers
ASIM Products 125 Products with ASIM support
Statistics - Comprehensive statistics and metrics
Interactive Index - Sortable/filterable HTML view

CSV Downloads

Download the generated outputs from Azure-Sentinel solution_analyzer_output at 2496f42ce0. Only generated analysis outputs are published here, not configuration, overrides, or connector history.

Documentation snapshot: These downloads match the documentation's analysis data: 584 solutions, 724 unique connectors, and 247 ASIM parser rows (231 source and 16 unifying). CSV row totals describe catalog entries, not necessarily individual pages, so they can differ from the page counts above. The existing output-branch CSVs were copied without rerunning the analyzer or regenerating the full documentation.

CSV file Contents
solutions.csv Solution metadata and Marketplace status
connectors.csv Connector metadata and collection methods
tables.csv Tables referenced by solutions
content_items.csv Analytic rules, hunting queries, and other content
parsers.csv Non-ASIM parsers
asim_parsers.csv ASIM parsers and schema associations
solutions_connectors_tables_mapping.csv Full solution, connector, and table mapping
solutions_connectors_tables_mapping_simplified.csv Simplified solution, connector, and table edges
content_tables_mapping.csv Content-to-table relationships
connector_table_ingestion.csv Per-table connector ingestion methods and APIs
playbook_connectors.csv Logic App connectors used by playbooks
solution_dependencies.csv Explicit and ASIM-derived solution dependencies
table_schemas.csv Unified table column schemas
tables_reference.csv Microsoft table reference metadata
la_table_schemas.csv Azure Monitor and Defender XDR column schemas
asim_fields.csv ASIM schema field catalog
asim_entity_fields.csv ASIM entity fields
asim_logical_types.csv ASIM logical types and allowed values
asim_vendors_products.csv ASIM vendors and products
solutions_connectors_tables_issues_and_exceptions_report.csv Analysis issues and exceptions
asim_parsers_unmatched_report.csv ASIM parsers without connector associations
asim_extraction_failures.csv ASIM field extraction diagnostics
artifact_doc_links.csv Documentation artifact Markdown and HTML links

Notes

⚠️ Unpublished: This item's solution is marked as unpublished in the documentation's source data. This is a solution publication status, not an indication of whether it is installed in your workspace.

🚫 Deprecated: This connector has been deprecated and may be removed in future versions.

Directory Structure

├── solutions-index.md      # Main solutions listing
├── connectors-index.md     # Data connectors listing
├── tables-index.md         # Log tables listing
├── methods-index.md        # Collection methods listing
├── statistics.md           # Statistics and metrics
├── csv/                    # Downloadable generated analysis CSVs
├── methods/                # Individual collection method pages
├── logic-apps/             # Logic App connector and action pages
├── solutions/              # Individual solution pages
├── connectors/             # Individual connector pages
├── tables/                 # Individual table pages
├── content/                # Content item pages
│   ├── content-index.md    # Content items listing
│   └── *.md                # Individual content pages
├── parsers/                # Non-ASIM parser documentation
│   ├── parsers-index.md    # Parsers listing
│   └── *.md                # Individual parser pages
└── asim/                   # ASIM parser documentation
    ├── asim-index.md       # ASIM parsers index by schema
    ├── asim-products-index.md  # ASIM parsers index by product
    └── *.md                # Individual parser pages

Markdown pages have sibling .html pages. The interactive index and its css/ and js/ assets are at the site root, outside this documentation directory.

Source

This documentation is generated from the Azure-Sentinel repository using the Solutions Analyzer tool.

Generating Fresh Documentation

From an Azure-Sentinel checkout, generate fresh local analysis data, then publish to the separate sentinelninja checkout (replace the example site-root path):

Set-Location "Tools\Solutions Analyzer"
$siteRoot = "C:\path\to\sentinelninja"
python collect_table_info.py               # Reuse cached table metadata
python map_solutions_connectors_tables.py  # Generate CSVs
python generate_connector_docs.py --skip-input-generation --output-dir "$siteRoot\Solutions Docs" --html-output-dir "$siteRoot" --html-docs-path "Solutions Docs/" --html-index-url "https://oshezaf.github.io/sentinelninja/index.html"

With the updated generator, the documentation command also copies its actual analysis inputs into Solutions Docs\csv. Always specify --output-dir; do not generate documentation inside Azure-Sentinel. The documentation generator does not run the mapper. The --html-index-url option keeps Markdown navigation linked to the published interactive index.

Reusing Published CSVs

Existing published analysis data is authoritative on solution_analyzer_output, not master or a development checkout. --skip-input-generation does not select a branch or verify freshness, and --input alone can mix the selected mapping with other local default inputs. Use a complete, pinned output-branch snapshot instead of blindly reusing a stale or empty output worktree.

Run this preparation from Tools\Solutions Analyzer in an Azure-Sentinel checkout, using the updated generator. It verifies the remote branch head, requires that commit to be available locally, extracts an immutable snapshot outside OneDrive without switching branches, and checks all 23 publication files:

$repo = (git rev-parse --show-toplevel).Trim()
if ($LASTEXITCODE -ne 0) { throw "Cannot locate repository" }
$remoteHead = @(git ls-remote origin refs/heads/solution_analyzer_output)
if ($LASTEXITCODE -ne 0 -or $remoteHead.Count -ne 1) { throw "Cannot verify output-branch head" }
$publishedCommit = ($remoteHead[0] -split '\s+')[0]
git cat-file -e "$publishedCommit^{commit}"
if ($LASTEXITCODE -ne 0) { throw "Commit is not local. Fetch origin solution_analyzer_output explicitly, then retry." }
$snapshot = Join-Path $env:TEMP ("solution-analyzer-output-" + [guid]::NewGuid())
New-Item -ItemType Directory -Path $snapshot -ErrorAction Stop | Out-Null
$archive = Join-Path $snapshot "output.tar"
git -C $repo archive --format=tar "--output=$archive" $publishedCommit -- "Tools/Solutions Analyzer"
if ($LASTEXITCODE -ne 0) { throw "Cannot archive verified output commit" }
tar -xf $archive -C $snapshot
if ($LASTEXITCODE -ne 0) { throw "Cannot extract output snapshot" }
$csvRoot = Join-Path $snapshot "Tools\Solutions Analyzer"
python -c "import pathlib,sys; from generate_connector_docs import PUBLISHED_ANALYSIS_CSVS; root=pathlib.Path(sys.argv[1]); missing=[n for n in PUBLISHED_ANALYSIS_CSVS if not (root/n).is_file()]; sys.exit('Incomplete published snapshot: '+', '.join(missing) if missing else 0)" $csvRoot
if ($LASTEXITCODE -ne 0) { throw "Published snapshot is incomplete; refusing local fallback" }
$siteRoot = "C:\path\to\sentinelninja"

Choose one operation after preparation. For a copy-only update, preserving the published artifact links:

python -c "import pathlib,sys; from generate_connector_docs import PUBLISHED_ANALYSIS_CSVS,publish_analysis_csvs; root=pathlib.Path(sys.argv[1]); publish_analysis_csvs({n:root/n for n in PUBLISHED_ANALYSIS_CSVS}, pathlib.Path(sys.argv[2]))" $csvRoot "$siteRoot\Solutions Docs"
if ($LASTEXITCODE -ne 0) { throw "Published CSV copy failed" }

Alternatively, to regenerate documentation from that snapshot, supply every CSV input flag. Supplemental catalogs and reports are taken from the same snapshot:

$csvInputs = @(
    "--input", (Join-Path $csvRoot "solutions_connectors_tables_mapping.csv"),
    "--connectors-csv", (Join-Path $csvRoot "connectors.csv"),
    "--solutions-csv", (Join-Path $csvRoot "solutions.csv"),
    "--tables-csv", (Join-Path $csvRoot "tables_reference.csv"),
    "--tables-overrides-csv", (Join-Path $csvRoot "tables.csv"),
    "--content-items-csv", (Join-Path $csvRoot "content_items.csv"),
    "--content-tables-csv", (Join-Path $csvRoot "content_tables_mapping.csv"),
    "--playbook-connectors-csv", (Join-Path $csvRoot "playbook_connectors.csv"),
    "--parsers-csv", (Join-Path $csvRoot "parsers.csv"),
    "--asim-parsers-csv", (Join-Path $csvRoot "asim_parsers.csv"),
    "--solution-dependencies-csv", (Join-Path $csvRoot "solution_dependencies.csv"),
    "--table-schemas-csv", (Join-Path $csvRoot "table_schemas.csv")
)
python generate_connector_docs.py @csvInputs --skip-input-generation --output-dir "$siteRoot\Solutions Docs" --html-output-dir "$siteRoot" --html-docs-path "Solutions Docs/" --html-index-url "https://oshezaf.github.io/sentinelninja/index.html" --artifact-links-csv "$snapshot\artifact_doc_links.csv"
if ($LASTEXITCODE -ne 0) { throw "Documentation publication failed" }

Use the copy-only command or the documentation command, not both. Documentation generation deliberately regenerates artifact_doc_links.csv for its pages; copy-only reuse preserves the pinned output branch's artifact CSV. These examples require the updated local generator; the automatic-copy changes are not yet published upstream.


Documentation generated by Solutions Analyzer. Overview and CSV download links updated November 2026; other documentation pages were not regenerated.